Access to the path 'C:\Windows\system32\config' is denied
I am using Katmai Feb 2008 CTP on 64 bit enterprise vista.I am getting following error, when I am trying to adddafult detail attributes with a role in report model.
getting the same error when trying to addfilter in a report model.Access to th path 'C:\Windows\system32\config' is denied.
..Aqurs
April 2nd, 2008 4:00pm
..Hey no one have any clue..??????????????????
..
Aqurs
Free Windows Admin Tool Kit Click here and download it now
April 9th, 2008 7:42pm
I believe you can avoid this in Vista by running Visual Studio as Administrator.
April 16th, 2008 2:17am
I am getting this same message. I am running Vista and running Visual studio as Administrator. My user account is also in the administrator group. I am getting this when trying to edit an attribute of a reporting model in BIDS for SQL Server 2005. Any other ideas would be appreciated.
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2008 10:11pm
I received the same error. I just closed the solution and re-opened - but not from File -> Recent Projects. Try navigating to the solution through windows explorer and launch the app directly from the sln file. The error disappeared for me.
May 1st, 2008 11:23am
The error disaapears , but now I cannot deploy...says access denied...??
Have to get out and restart as "priveledged" user, for deploy to work...
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2008 10:18am
That worked for me too. Thanks
May 31st, 2008 6:52am
Lauching the 'Report Model.sln' directly works. The error disappears and when you right-click in the'Detail View' and create a 'New -->Expression' you get to the 'Define Formula' dialog boxrather than get the error message 'Access ... is denied'
Free Windows Admin Tool Kit Click here and download it now
July 22nd, 2008 2:01am
Good Job Eric!
I tried your solution and it worked! Thanks!
September 12th, 2008 1:22am
Surprisingly enough, running my sln from Windows Explorer instead of the recent list worked for me too! I was able to access the Expression popup and deploy just fine.
Nice work, bpeter and Eric Lindberg---thanks for taking the time to post.
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2008 6:38pm
Yep, I had the same problem and I closed Visual Studio and started up the sln from windows explorer. Bizarro is all I can say. Thanks for the tip on what to do.KathyL
December 19th, 2008 4:54pm
The answers here are all work arounds, much appreciated as they are, but what is the cause of the problem and what permissions should be granted?
Actually found it here;
https://connect.microsoft.com/SQLServer/feedback/details/334796/model-designer-fails-on-acces-to-c-windows-system32-config?wa=wsignin1.0
Set the startup folder for BIDS in Start menu to "%ProgramFiles%\Microsoft Visual Studio 8\Common7\IDE\". Right click on the Visual Studio shortcut in your start menu, select "Properties," then
set the Start in property.
On 64-bit Windows 7, "Program Files" is "Program Files (x86)"
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2010 11:14am
Visual Studio apparently needs to create a file named "config" and when the working directory is not available for writing (due to UAC or other restrictions), it will then try to write to the system32 folder. If you cannot write to Program Files then likely
you cannot write to the system32 folder either. This is why running Visual Studio as administrator solves the problem, it gives you write permission to Program Files and System32 so no matter where it wants to put the file it can. I think that likely setting
the startup folder fixes the issue on systems where you have write access to Program Files but not System32. Browsing and running the solution file directly change the startup folder for BIDS to be the folder the solution resides in which, if you have access,
will fix the problem as well but you will see it create the file named "config" in that folder.
So really this is a security permission/UAC/startup folder location error. Depends on your system setup, your user access permissions, and personal preference as how you want to go about fixing it. Disabling UAC would probably fix it in some cases as well,
but I wouldn't call that a very good solution at all.
May 17th, 2012 1:38am